-
-
Notifications
You must be signed in to change notification settings - Fork 934
web: Add config option to hide message when Ruffle restores from bfcache #22226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
web: Add config option to hide message when Ruffle restores from bfcache #22226
Conversation
|
Can we make it an enum that select whether to restore, reload, or ask the user? |
|
In the reload scenario, how would we want that to work? Calling |
|
Added reload, but the content does briefly blink as the page itself has restored from the bfcache. Screencast.From.2025-11-13.16-01-59.mp4 |
|
The enum is |
7cab140 to
2752865
Compare
kjarosh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you! <3
35172bf to
7d976a9
Compare
|
Honestly I would prefer if we removed the message entirely. I find it annoying and not useful. Or we could at least change the default behavior. |
This adds a configuration option,
hideRestoredMessage, which hides the message that appears when Ruffle is restored from the bfcache. This message was added when Toad06 switched from the unload event to the pagehide event, enabling use of the bfcache.Note that the bfcache is never used with Ruffle on Chromium due to a "bug" (previously intended behavior), therefore this more-so affects Gecko (Firefox). See https://issues.chromium.org/issues/424552566. Basically, Adobe Flash Player would not work with the bfcache, so Chromium disables the bfcache on pages with embeds or objects that have SWF sources. Since modern Chromium no longer supports any plugins, including Flash, this is now unneeded code on Chromium's part.